All rsyslog-generated log files must have mode 0600 or less permissive.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
RHEL-06-000135	RHEL-06-000135	RHEL-06-000135_rule		Medium

Description
Log files can contain valuable information regarding system configuration. If the system log files are not protected unauthorized users could change the logged data, eliminating their forensic value.

STIG	Date
Red Hat Enterprise Linux 6 Security Technical Implementation Guide	2013-02-05

Details

Check Text ( C-RHEL-06-000135_chk )
To see the permissions of a given log file, run the following command: $ ls -l [LOGFILE] The permissions should be 600, or more restrictive. If the permissions are not correct, this is a finding.

Fix Text (F-RHEL-06-000135_fix)
The file permissions for all log files written by rsyslog should be set to 600, or more restrictive. These log files are determined by the second part of each Rule line in "/etc/rsyslog.conf" and typically all appear in "/var/log". For each log file [LOGFILE] referenced in "/etc/rsyslog.conf", run the following command to inspect the file's permissions: $ ls -l [LOGFILE] If the permissions are not 600 or more restrictive, run the following command to correct this: # chmod 0600 [LOGFILE]

Fix Text (F-RHEL-06-000135_fix)

The file permissions for all log files written by rsyslog should be set to 600, or more restrictive. These log files are determined by the second part of each Rule line in "/etc/rsyslog.conf" and typically all appear in "/var/log". For each log file [LOGFILE] referenced in "/etc/rsyslog.conf", run the following command to inspect the file's permissions:

$ ls -l [LOGFILE]

If the permissions are not 600 or more restrictive, run the following command to correct this:

# chmod 0600 [LOGFILE]